Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@apps/cli/src/lib/init.ts`:
- Around line 617-628: The code path handling empty repos only uses
initOpts.directories[0] and silently drops additional repeatable --directory
values; update the logic in the branch that checks dirGroups.size === 0 to
either iterate over initOpts.directories and set selectedDirectories to all
provided values (so every requested directory is scaffolded), or explicitly
reject multiple values when initOpts.nonInteractive is true by validating
initOpts.directories.length and throwing/printing an error; modify the block
referencing initOpts.directories, dirName, selectedDirectories and the
prompter.text fallback to preserve or validate all entries rather than only
using the first one.
- Around line 61-76: The parsing logic currently allows empty inline values for
flags like --directory, --directories, and --default-locale to slip through;
update the flag-handling code so inline empty values are validated the same as
space-separated forms by reusing or mirroring readInitFlagValue's check: when
you detect a flag token that may contain an '=' (e.g., '--directory=' or
'--default-locale='), treat an empty string after '=' as missing and throw the
same RuntimeError({ code: "INVALID_INPUT", message: `Flag "${flag}" requires a
value.`, statusCode: 400, details: { flag } }) used in readInitFlagValue;
alternatively call readInitFlagValue for space-separated cases and add a utility
that validates and rejects '' for '='-style tokens in the code paths that
currently handle --directory, --directories, and --default-locale (also apply
the same change to the other flag parsing block mentioned around the other
parsing function).

In `@skills/mdcms-brownfield-init/SKILL.md`:
- Around line 66-68: The line "Creates (or joins) the project and environment on
the server." incorrectly claims reuse; either remove "or joins" or explicitly
document the exact precondition/recovery path for the init command: state that
init will attempt to create the project/environment and will exit with an error
on project-create 409, describe what the caller should do on that error (e.g.,
manually join or pass an explicit flag), and reference the init behavior and the
project-create 409 response so readers know the expected flow.

In `@skills/mdcms-content-sync-workflow/SKILL.md`:
- Around line 92-120: The workflow's MDCMS push step uses the interactive-safe
command `npx mdcms push --validate`, which will skip new/deleted candidates in
non-interactive CI and can cause schema sync failures; update the `MDCMS push`
job to run a headless-safe command such as `npx mdcms push --validate --force`
(and add any CLI flag your tool uses for non-interactive confirmation like
`--yes` or `--confirm` if available) so pushes on `content/**` or
`mdcms.config.ts` changes apply created/deleted items and schema updates
reliably; modify the `run:` line under the `MDCMS push` step to include these
flags.
- Around line 135-138: Update the SKILL.md bullet that instructs readers to
"check `mdcms push --help` for the current deletion flag" because the CLI
doesn't expose a dedicated deletion flag; instead, reword the text to explain
that deletions are handled interactively by `mdcms push` (it will classify "both
modified" or prompt before deleting) and mention the actual available flags
(`--force`, `--dry-run`, `--validate`, `--published`, `--sync-schema`) and how
`--force` affects deletion behavior (non-interactive overwrite). Refer to the
`mdcms push` command and the `--force`/`--dry-run` flags when updating the
paragraph.

In `@skills/mdcms-sdk-integration/SKILL.md`:
- Around line 55-65: Replace the incorrect SDK calls and shape assumptions: use
the SDK methods cms.get(type, input) and cms.list(type, input?) instead of
getDocument/listDocuments, and update any downstream usage to expect the
paginated envelope returned by list (access the items via the .data property,
e.g., iterate over posts.data rather than posts); update examples that showed
const about = ... and const posts = ... to call cms.get("page", { path: "about"
}) and cms.list("post", { limit: 20 }) semantics and adjust subsequent code to
use the list response's data field.

In `@skills/mdcms-self-host-setup/SKILL.md`:
- Around line 40-43: The checklist uses the wrong S3 env-var prefix
`MDCMS_S3_*`; update the doc to reference the correct storage env names `S3_*`
(e.g., replace any occurrence of `MDCMS_S3_*` with `S3_*`) so they match the
server/compose contract; double-check related mentions (the checklist item
listing `Database credentials`, `S3/MinIO credentials`, `Auth provider
settings`, and `MDCMS_STUDIO_ALLOWED_ORIGINS` / `<Studio />`) and adjust only
the S3 variable names to `S3_*` while leaving other env names unchanged.

In `@skills/mdcms-setup/SKILL.md`:
- Around line 36-44: The repo-scan heuristic that runs the find command will
pick up the skill pack’s own SKILL.md and misclassify empty repos as brownfield;
update the detection used before invoking
mdcms-brownfield-init/mdcms-greenfield-init to exclude skills/ and other
docs-only paths (e.g., skills/*/SKILL.md, docs/, .github/) or restrict the
search to likely content roots (e.g., content/, pages/, docs/content/) so only
true user-managed Markdown/MDX files trigger mdcms-brownfield-init; ensure the
same exclusion logic is applied where the check is repeated (lines referenced
around the find invocation and the branch that calls
mdcms-brownfield-init/mdcms-greenfield-init).

---

Outside diff comments:
In `@apps/cli/src/lib/init.ts`:
- Around line 1077-1081: The outro always reports "Example post created" because
it checks scaffoldedType which is set for every init; instead, gate the
stdout.write on whether the example file was actually created: add a boolean
(e.g., exampleCreated) that is set to true where the example post write occurs
(the branch that currently writes the example file) and set false when the
--no-example-post path skips it, then change the final message that uses
scaffoldedType/selectedDirectories to only run if exampleCreated is true;
reference the existing symbols scaffoldedType, selectedDirectories and the
example-file write branch to locate where to set and check exampleCreated.